Intelligent title cache system

ABSTRACT

Embodiments of the invention relate to an intelligent title cache system and more particularly to an automated graphical system for replacing potentially lengthy graphics rendering from a wide range of graphics generating systems with very fast assembly of 2D pre-rendered images into a complete video frame. This ensures minimum latency and consistent, predictable processing overheard, regardless of how complicated the render itself may be. Moreover, the intelligent title cache system is configured to prepare the majority of cached images ahead of time for all frequently used values.

RELATED APPLICATIONS

This application claims the benefit of priority of U.S. application Ser.No. 15/441,160, filed Feb. 23, 2017, which is a continuation ofapplication Ser. No. 15/216,397, filed Jul. 21, 2016, which are hereinincorporated by reference to the present application.

FIELD OF THE INVENTION

The present invention relates generally to an intelligent title cachesystem and more particularly to a title cache system for replacingpotentially lengthy graphics rendering with very fast assembly of 2Dpre-rendered images into a complete video frame. This ensures minimumlatency and consistent, predictable processing overheard, regardless ofhow complicated the render itself may be.

BACKGROUND

In the world of title and graphics animation as it applies to3-Dimensional (3D) Real Time Rendering, the standard approach torendering complex visual 3D models for real time playback, includingreal time data updates (for example sports scoreboards, stock tickers,weather, news, and all manner of live graphics used in broadcastproduction that are meant to display up to date information as it comesin) is to build hardware graphics systems that are powerful enough toaccomplish converting data into graphics in real time. However, thisalways puts an upper limit of aesthetic complexity and necessitates veryexpensive hardware. Meanwhile, the dramatic rise in low cost computerswith decent graphics ability and explosion of live streamed broadcastingnecessitates the need for an affordable way to create responsive, yetaesthetically complex, animated graphics on a wide range of systems.

Similarly, in the world of title and graphics animation in 2-Dimensional(2D) Real Time Rendering applications, the standard approach for fast 2Drendering and drawing alphanumeric values or characters efficiently isto create images of each character and then position them at theappropriate position in the display output such as a monitor ortelevision. For example, to display “00:00”, the general method is totake the rendered “0” and draw it onto the display four times, eachoffset by the appropriate amount. This approach is very efficient, butcan have several drawbacks such as 1) It may be very specific, requiringknowledge of everything necessary to position the letters, includingkerning and other font information; 2) If the design intends to showdifferent digits in different ways (for example, increasing the size andchanging the shading of the leading digit), this information may becomeeven more specific and complicated; and 3) It limits the render to onlyletters. However, depending on the design of the title and graphicstemplate, it may be desirable to interpret the data value in an entirelydifferent way.

What is highly desirable is a title and graphics animation productionand playback mechanism which does not become involved in the specificdetails of the actual graphics rendering methodology used to create aparticular result, but instead can be applied to many different graphicsrendering engines with the intended goal of converting such systems,that rarely can render in real time, into fully responsive real timegraphics systems. Such a system should have the power of the full 3Dsystem as well as the speed and efficiency of the 2D display system.Additionally, what is needed is a rendering production mechanism that iscompletely removed from any creative aspects of the title and graphicdesign itself. Graphic designers should not be required to focus on theimplementation and real time performance details of their designs.Conversely, implementers of the systems should not be required tounderstand and work around the requirements of the specific design andrender technology.

SUMMARY

This invention defines a title caching mechanism for replacingpotentially lengthy graphics rendering with very fast assembly of 2Dpre-rendered images into a complete video frame. This mechanism may beimplemented and performed using a software or firmware application. Itoffers this capability through a flexible but consistent mechanism thatcan easily be used by a wide range of applications with differingrequirements. In particular, an objective in this document is to providean intelligent title caching system which does not itself engage in theactual rendering process of text, graphics and animation, but whenapplied to a specific graphics rendering engine, manages the renderingof text and graphics in such a way as to achieve improved optimization,efficiency and speed enhancement of the overall title processing system.

In particular, in the intelligent title caching system a Title iscomposed of a template and a number of variables in the template and anInput may determine which variables are dynamic. In this system, dynamicvariables are each rendered in their own layer. All other variables maybe set once and rendered in a background layer. In addition, dynamicvariables can play in sync with the rest of the title, or independently.In some instances, playback of the title may be from the start to apause point, and then to the end. Similarly, dynamic variables maystart, pause, and stop payback independently. Playback of a variableconsiders its relation to the pause point. For example, to change avisible value, the system is configured to play from pause to out, andthen inserts a new value, playing from in to a pause point. Tomomentarily view the value, the system plays it from in to out, withoutstopping. In another instance, the Input can specify a set of expectedvalues for a variable, so they can be precomputed and cached. Whenvariables are not cached, the system may play back the request bymanaging the rendering of the missing variable from the renderingengine, waiting for the new value to render, and then playing it.

Benefits and Advantages of system include, for example, 1) dataindependent rendering; 2) highly efficient playback driven byintelligent understanding of the component data as well as knowledgethat full 3D render of a scene is much more compute intensive thanoverlaying precomputed bitmaps; and 3) By offloading the 3D graphicsengine, it is possible to run the system on a wide range of computers,from simple processors with onboard graphics software to powerful GPUsystems.

BRIEF DESCRIPTION OF THE DRAWINGS

Various other objects, features and attendant advantages of the presentdisclosure will become fully appreciated as the same becomes betterunderstood when considered in conjunction with the accompanyingdrawings, in which like reference characters designate the same orsimilar parts throughout the several views, and wherein:

FIG. 1 is a block diagram representing an exemplary general-purposecomputing environment into which aspects of the subject matter describedherein may be incorporated;

FIG. 2 illustrates a block diagram of an object model of an intelligenttitle cache system and related components thereof, according to anembodiment.

FIG. 3 illustrates a time-based illustration of the title template ofthe title cache system, according to an embodiment.

FIG. 4 illustrates a block diagram of a scheduling Application ProgramInterface representation of the intelligent title cache system,according to an embodiment.

FIG. 5 illustrates a block diagram of an example of a MultistateVariable applied to a sporting event scenario, according to anembodiment.

FIG. 6 illustrates a block diagram of an object representation of theTitleCache, according to an embodiment.

FIG. 7 illustrates a block diagram of the integration and implementationof the TitleCache class in the title cache system, according to anembodiment.

FIG. 8 illustrates a block diagram of a file representation of an XMLTitleCache definition, according to an embodiment.

FIG. 9 illustrates a flowchart of building a representation of the titleof the cache system, according to an embodiment.

FIG. 10 illustrates a flowchart of the frame rendering by the renderengine of the title cache system, according to an embodiment.

FIG. 11 illustrates a block diagram of a Multipart Variable, accordingto an embodiment.

FIG. 12 illustrates a display output of a constantly changing timevalue, where individual digits are pre-rendered alone, per the overallgraphics design, and then composited in real time to create the completetext, according to an embodiment.

FIG. 13 illustrates a block diagram of the intelligent title cachesystem and external render engines, according to an embodiment.

FIG. 14 illustrates a flowchart of the intelligent title cache system,according to an embodiment.

DETAILED DESCRIPTION

FIG. 1 illustrates an example of a suitable computing system environment100 on which aspects of the subject matter described herein may beimplemented. The computing system environment 100 is only one example ofa suitable computing environment and is not intended to suggest anylimitation as to the scope of use or functionality of aspects of thesubject matter described herein. Neither should the computingenvironment 100 be interpreted as having any dependency or requirementrelating to any one or combination of components illustrated in theexemplary operating environment 100.

The computing environment 100 may include a system board 110(alternatively known as the mainboard, motherboard, baseboard, planarboard or logic board) which implemented on a printed circuit board(PCB). It provides communication between many of the electroniccomponents of the system operating components, such as a centralprocessing unit (CPU) and memory, and provides connectors for otherperipherals. Hardware elements related to the system board 110 include,for example, memory components defined by a system memory using ReadOnly Memory ROM 131 and Random Access Memory RAM 132 circuitry, acentral processing unit CPU 120 being defined by a microprocessingcircuit, a system bus 121 having physical wiring bus elements totransfer binary data between each hardware components, and multipleexternal interfaces including a video interface 190, an outputperipheral interface 195, non-removable and removable memory interfaces(140, 150), a user input interface 160, and a network interface 170.External hardware components of the system board 110 may include adisplay monitor 191, printer 196, speakers 197, keyboard 162, a pointingdevice or mouse 161, and a local area network 171 interfacing to remotecomputers 180. Software, programs data, and firmware may be applied toand installed on the system memories (131, 132) and provide instructionsto operate the computing system 100. A BIOS 133 for providing a set ofcomputer instructions in firmware that control input and outputoperations of the computer system 100 may be installed in the ROM 131.Applications related to software include an operating system OS 134,applications programs 135, other program software modules and drivers136, and program data 137. Software may also be loaded and operated viastorage devices such as hard drive 141, disk drive 151 via disk 152, andcompact disk drive 155 via compact disk CD 156. The storage device mayinclude and execute software such as an operating system 144,application programs 145, other program modules 146, and program data147.

Aspects of the subject matter described herein are operational withnumerous other general purpose or special purpose computing systemenvironments or configurations.

Examples of well-known computing systems, environments, orconfigurations that may be suitable for use with aspects of the subjectmatter described herein comprise personal computers, server computers,hand-held or laptop devices, multiprocessor systems,microcontroller-based systems, set-top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers, personaldigital assistants PDAs, gaming devices, printers, appliances includingset-top, media center, or other appliances, automobile-embedded orattached computing devices, other mobile devices, distributed computingenvironments that include any of the above systems or devices, and thelike.

Aspects of the subject matter described herein may be described in thegeneral context of computer-executable instructions, such as programmodules, being executed by a computer. Generally, program modulesinclude routines, programs, objects, components, data structures, and soforth, which perform particular tasks or implement particular abstractdata types. Aspects of the subject matter described herein may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote computer storage mediaincluding memory storage devices.

The computing system environment 100 may also have or may execute avariety of operating systems OS, including an operating system used on adesktop platform or a mobile operating system used mobile devices suchas smartphones, cellular/mobile phone, tablets, personal digitalassistance PDA, laptop computer, smart watches, and the like. Thecomputing system environment 100 may also include or may execute avariety of possible applications or “Apps”, such as musicstreamers/players, e-book readers, utility Apps, and electronic gamingapps. The application may provide connectivity and communication withother devices or a server over a network, such as communicating withanother computer via a wired or wireless Internet or Intranet networkfor online interaction such as electronic gaming or onlinecollaboration.

Intelligent Title Cache System—Object Model

FIG. 2 illustrates a block diagram of an object model of an intelligenttitle cache system 200 and related components thereof, according to anembodiment. Components of the intelligent title cache system 200 mayinclude 1) a data input source 201, 2) a data input handler 203 coupledto the media input 201 and configured to receive data therefrom, 3) ascheduler 205 coupled to an output of the data input handler 203, 4) aproject component 207 coupled to an output of the of the scheduler 205and an output of a render engine 209, and 5) a plurality of outputdevices 211 coupled to the project component 207 via a channel mixer213. Each of the components (201-213) may include one or moresubcomponents that are responsible for handling and processing datareceived by their corresponding components. For example, the data input201 may include a service input 215 and one or more file inputs 217, thedata inputs 203 may include a plurality of input profiles (219, 221),the scheduler 205 may include a queue 221, the project component 207 mayinclude a plurality of title templates 235 and a compositor 237subcomponent, and the plurality of output devices 211 may includemultiple devices such as HDMI 225, SDI 227, and DirectConnect 229.Details and applications of components (201-211) and sub-components(213-241) contained within system 200 are further described in hereinbelow.

1) Data Input Handler and Input Profiles

The input profiles (219, 221) of the data input handler 203 are alsoknown as “Behaviors”, and in some applications matching an input to atitle may be considered important. For example, an input that sends thetime of day may not be very useful when connected to a title that isdesigned to show the name of a contestant in a bike race. Thus, matchingthe input to the template is like matching the data to the display. TheInput Profile (219, 221) provides a method for a data source torepresent the variables that it manipulates, and in what methods, so itcan then be matched to a title correctly and also perform efficiently inthe overall rendering process, making sure that the data it is sendingcan be quickly turned into graphics which are displayed. For example,nothing much happens when a football scoreboard is connected to aweather reporting graphic. You want the data to be matched to thedisplay. And, within that, you want the data which is going to changequickly and frequently to be capable of doing so, and that is where thecaching mechanism excels, as will be further described in detail below.

In operation, each input profile (219, 221) is generally required tospecify which variables it sends while the title template 235 specifiesthe variables to which it can respond. Thus, the first objective of theinput profile is to match the behavior with a title that supports it.Next, the input profile is configured to provide some intelligence abouthow it intends to work with those variables, significantly impacting thereal-time performance of system 200.

To illustrate this point in a sporting event application, take forexample a scoreboard as a source for the data input 201, and considerfour variables defined on the scoreboard: Home Score, Clock, Possession,and Home Team Name. In this scenario,

-   -   The data input 203 expects to set the Score variable        infrequently.    -   The data input 203 expects to set the Possession every now and        then, but it knows that this will only be one of two values:        Home or Opponent.    -   The data input 203 expects to set the Clock every tenth of a        second. It knows that this too can be a predetermined set of        values.    -   The data input 203 does not set the Home Team Name—that should        be done before the game. It is unaware this variable exists.

In some instances, the input profile (219, 221) may handle each of theitems above as follows:

-   -   The input profile defines the score variable as one that will        change dynamically. Each time the score changes, a new score        must be rendered and composited onto the rest of the image.    -   For the Possession variable, it provides two image choices, one        for each direction.    -   For the Clock, it breaks down the string into sets for each        digit. So, a 4-digit clock might have 10 states for each digit.    -   It completely ignores the Home Team Name. This should be set        once and rendered into the background of the title.

Note that all variables, whether dynamic or preset, have timelines, soeach of these examples involves a timeline of the text or image firstentering and then exiting. These timelines may vary from variable tovariable. Moreover, the input profile (219, 221) may denote whichvariables are required to be in the title template and which areoptional.

In summary, the input profile (219, 221) may define a short set ofinformation that the data inputs 203 provides to accomplish thefollowing:

-   -   Describe a particular purpose, or behavior.    -   Find and match with appropriate title templates 235.    -   For performance optimization, identify which variables it will        be changing, and where appropriate, what all the values are        required to be.    -   Conversely, report back to the host (e.g., a data input service,        application, device, etc.) which variables are expected to be        manipulated.

2) Scheduler

In system 200, the scheduler 205 is generally responsible for managingthe entire system of playback, and all commands route through it. Someof these commands include, for example, actions to load projects, assignvariables, and trigger playback. Internally, the scheduler 205 maintainsa set of queues 221, to help sequence commands to the title templates235.

3) Render Engine

The Render Engine 209 of system 200 is generally responsible forperforming all 2D or 3D rendering and animation in the system 200, beingthe key tool for creating the animated imagery in this titlingtechnology. It may take as input a title template, with its variablesassigned, and generates an output series of frames such as, for example,the rendered title. However, it can also be instructed to render onlyspecific layers in other applications. Examples of the Render Engine 209may include software based render engines or hardware based graphics andanimation render engines and APIs, such as Unity, Direct3D and OpenGL.

4) Compositor

The compositor 237 takes one or more frame outputs from the RenderEngine 209 and blends together various title templates 235 to make afinished frame or video output 239 as shown in FIG. 2. The compositorreplicates the various blending modes available in the Render Engine,for combining multiple layers into one. These include standardtechniques, such as Alpha Blend, Stencil Blend, and more. In somepractical applications, techniques that the render engine might use tocombine two layers are replicated by the compositor 237. In other words,the compositor 237 may be used to replicate what the render engine uses,which primarily may be an alpha blend, for example. However, with mostgraphic and animation tools, there may be some exotic blending modes,for example “screen”, “color burn”, etc., in which each blending mode isa different formula for how to combine two pixels from two image layersinto one. And so, for each blending mode that the render engine uses,the compositor provides an equivalent implementation.

5) Channel Mixer

The video output 239 from the compositor 237 is received by the channelmixer 213 which combines the video output 239 from multiple titletemplates 235 on the same channel into one and then sends one or morecombined video outputs 241 for that channel to the output devices 211.In practice, the system 200 may implement a variety of channel mixers,including software based mixers and hardware based mixers such as, forexample, for combining the layers of images from all the titles into asingle one. In one implementation, the channel mixer 213 may simply bean alpha blend composite.

6) Variables and Rendering

Referring again to FIG. 2, the title templates 235 are organized tooptimize for rendering just what needs to change, and it does this in away that reflects the fact that it is the variables that drive thesedecisions.

The rendered title itself may be separated into three types of layers:

-   -   Variables that have predefined values and typically change        frequently. These can be rendered once, saved to cache, and used        multiple times.    -   Variables that always receive new values. These are rendered as        required and then discarded, or, if desired, kept and stored for        later use.    -   Everything else. These are all the variables that don't change        and all the background graphics, etc.

This determination of the layers is made by matching the input profile(219, 221) with the title template 235.

-   -   The title template templates 235 list all the variables it        supports, as well as when they occur and where they are in the        layer organization of the title templates 235 (including        compositing information so they can be rendered in afterwards.)    -   The input profile (219, 221) lists which variables it will        manipulate and, when applicable, all preset values the variable        can take.

In operation, the scheduler 205 and title 235 use this information toorchestrate the performance intelligently and efficiently.

7) Schedule( ) Command:

In system 200, a Schedule( ) command 243 essential to runtime operationfor triggering and controlling the flow animation and graphic events insystem 200. The Schedule( ) command 243 may be organized aroundvariables, since variables determine what particular information arerequired to be updated. For example, by running multiple Schedule( )commands 243 for different variables on one title template 235, thedifferent variables may independently update, even animatingasynchronously within one title template 235. Conversely, the samevariable across multiple title templates 235 can be scheduled to playsynchronously with one call.

The Schedule( ) command 243 may take several parameters, including, forexample:

-   -   a) Which title(s) to send it to. The address can be:        -   The name of a specific title. (“title” field)        -   The id of a specific title. (“title” field)        -   The name of an input behavior or input profile. All titles            that were set to this will receive it. (“input” field)        -   The name of the variable(s). All titles that use these            variables will receive it. (the “variable” field itself)    -   b) A set of variables and accompanying values. This can be empty        or any number of variables to set all at once.    -   c) Markers, indicating optional start and end points within the        title for the operation        -   These refer to the named markers that are embedded in the            templates, e.g., “Start” and “Pause”.        -   They can also be discrete time values, measured in seconds,            e.g., “0.23”    -   d) An Action command, indicating action to take, including        modifiers.    -   e) A time value. This is used to set the time this will occur.        It can be modified by the Action.

A named queue (optional): Queues may organize actions to play in anorder sequence and can have customized names. The queue may exist aslong as there are Actions placed in it, and then eventually discarded.

The Action command defined within the Schedule( ) command 243 may becomposed of multiple options and modifiers which are summarized andprovided in Table 1 below:

TABLE 1 “SetVars” // Set these variables. “Play” // Play it. “All” //Use all layers. “PlayOn” // Make this a fresh playback of this title.“PlayOff” // Make this finish the playback of this title. “Curate” //Require this to be blessed by the user first. “Loop” // Play theselected layers with a continuous loop. “Overlap” // When updating avalue, let the animations in and out overlap. “Render” // If variableschange, force a render, even for the background. // Region to play. Bydefault it uses the two named In and Out markers. These options overridethem. “SetInVar” // Set the in marker at the start of the earliestvariable in the list. “SetOutVar” // End at the time of the lastvariable in the list. “SetInPause” // Start at the pause point in themiddle of the template. “SetOutPause” // End at the pause point in themiddle of the template. “SetInTemplate” // Start at the start of thetemplate. “SetOutTemplate” // End at the end of the template.“SetOutEmpty” // End when the paragraph runs out of image. // Timing.These determine when this starts playback, and options for its behavior.“Override” // Clear out the queue and put this at the head. “Replace” //If there is an earlier queued item for this action, replace it.“Interrupt” // Kill the currently playing title as soon as this canstart. “Sync” // Make sure all layers are finished playing beforestarting. “First” // Put this at the head of the queue. “LockEnd” //Lock the end times of all layers with the time. “Render_Wait” // Ifstill rendering, force a wait. “Render_Skip” // If still rendering, playthe paused still frame. “Render_PickUp” // If currently playing, justjump in at this point with updated value. “Hold” // Wait until previousplay in queue is completed, then wait fTime. “Time” // Cue to play atthe specified absolute time. “Now” // Play immediately, or delayed byfTime amount. “Duration” // Make the playback last exactly the value inthe duration variable. // Combine the above for some useful presetActions: “Alert” // Alert means play the title from start to finish.“CutIn” // Cut In means start playback in the middle and hold there.“CutOut ” // Cut Out means stop immediately. “AnimateIn” // Animate Inmeans start at the beginning and play up to the hold point. This isstandard to bring in an overlay. “AnimateOut” // Animate Out means startat the hold point and play through the end. // Also, make sure allplaying variables finish first. // This is standard to conclude anoverlay. “Update” // Refreshes the selected variable(s) at the holdpoint, with animation. “Prep” // Get the template ready to play, butdon't actually do anything. “TightLoop” // Loop the specified var(s)with no delay between loops. “IntervalLoop” // Loop the specifiedvars(s), delay set by the entire template. “Crawl” // Plays thespecified vars until they have no letters left. “Play_Once” // Plays theselected variables from start to finish.

FIG. 3 illustrates a time-based illustration of the title template 235of system 200. Each title template 235 may be characterized as agraphics generating document having three primary components: Markers301, Layers 303, and Variables 305 contained within a timeline 307.Markers 301 may denote specific points in the title timeline 307. Theseare generally used to control the playback to known points on thetimeline 307. For example, a “Start” marker 309 may indicate thebeginning of the start sequence, usually used to “fly” the title inwhile a “Pause” marker 311 may indicate the point half way through wherethe display should hold for a while, and so it also marks the start ofthe final sequence that usually flies the title back out. In someapplications, the “Pause” marker may be important because may beattributed to how individual layers are designed to update with newinformation. Layers 303 are defined in this document as individualgraphic sequences that overlay each other, top to bottom, and animateover time. They can be any kind of imagery, from solids to pictures totext, for example. Individual layers can asynchronously play on theirown timelines. However, they may all share the same pause point, whichrepresents the moment when everything is displayed such that it can holdstill for a while.

Variables 305 are defined in this document as receptacles for data thatis displayed in the layers 303. Variables 305 manage images, text, evencolors. Of these, the most frequently used are text variables, which mayprovide text to place in a layer. In all cases, variables 305 arecommunicated purely as text strings. The cache system 200 generally doesnot understand, and is not required to know, anything about the data ina variable 305 other than that it is represented with a text string. Forexample, a title template 235 may be designed to represent the string“01” with two numeric letters, or it might display the image of a goosehead on a spring. The point here is that all the communication occurs astext strings, whether they are floating point numbers, RGB colordefinitions, file addresses of images, or the words “true” and “youlied”.

Intelligent Title Cache System—Scheduling API

FIG. 4 illustrates a block diagram of a scheduling Application ProgramInterface (API) representation of the intelligent title cache system200. The API representation provides an enhanced view of several APIelements (403-409) driving the components (201-213), including theoperational interactions between these components and subcomponents ofthe intelligent title cache system 200. These API elements (403-409) mayinclude, for example, a Service Handler API 403, a Scheduler API 405,and an Output Device API 407 for driving the data input handler 203, theScheduler 205, a Channel/Playlist 409, and the Output Device 211 insystem 200, respectively. In some other embodiments, other componentsand subcomponents may be included in system 200 such as, for example,one or more HTTP Input data 415 components, a Service Handler 417subcomponent and a Script Handler 419 subcomponent associated with theService Handler API 403, one or more Input Behavior 421 subcomponentsassociated with the Service Handler 417 subcomponent, one or more InputBehavior 423 subcomponents associated with the Script Handler 419, aQueue 425 and a Channel List 427 associated with the Scheduler API 405,one or more TitleInstances 429 and a Channel 431 subcomponent associatedwith the Channel/Playlist 409, a template 433 and a Multipart Cache 435associated with the TitleInstances 429, multiple output devices NDI 437,DirectConnect 439, WireCast 441, DeckLink 443, and HDMI 445 associatedwith the Output Device API 407, a Meta Data Parser 447 component, and atitle software user interface TPL UI 449 component.

TitleCache Class

A TitleCache class of the system 200 may optimize playback bydetermining which components of the title animation can be pre-renderedand which need to be prepared dynamically or “on the fly”. This is alldetermined by which variables are in use in the template and how theyare used.

Variables within a template fall into three categories:

-   -   Fixed. These are variables that are set once by the user in set        up and then they are never changed during playback. These        include variables that set information that is fixed and        unchanged during a broadcast. Examples would be “Home Team” or        “Background Color”    -   Predefined. These are variables that will change during the        broadcast, but they will only pick from a predefined set of        states. Examples might include “Inning”, “Strikes”, or        “Countdown Clock”.    -   Dynamic. These are variables that change during broadcast and        can take on an unlimited range of values.

Knowledge of whether a title variable is Fixed, Predefined, or Dynamicis determined by two things:

-   -   The Template itself, which simply defines all of the available        variables.    -   The Input, which specifies:        -   Which variables it uses.        -   Which variables are pre-defined.        -   For predefined variables, all the different values.

Once the TitleCache class knows the behavior of each variable, it canconstruct a much more intelligent representation of the title in memory,breaking the representation down into one or more layers, which followthese rules:

-   -   One or more fixed layers, including the background layer, that        span the full length of the title and includes:        -   All fixed imagery within the title.        -   All imagery that is driven by fixed variables.        -   Fixed imagery that may appear in front of some of the titles            (and so must be a separate fixed layer from the background            fixed layer.)    -   For each predefined variable, a layer is created that manages        all predefined variations of that variable. These renderings        span the duration of the variable and typically have        transparency so they easily composite on top of other layers,        including the background layer.    -   For each dynamic variable, a layer is created, but no renderings        attached until it is given a value.

Prior to playback, the background and predefined variable layers arecompletely pre-rendered, and their frames are made available as a framecache, either in memory or in a file. The frame cache may be implementedboth in memory as a memory frame cache or disk such as a file framecache.

In a project work environment, this same cache can be saved to disk andthen reloaded when the project is reopened. This cache gets completelyregenerated if anything that changes the background layer or thepredefined variables occurs. For example, conditions for regeneratingthe cache may occur when:

-   -   the template is edited or replaced with a different one.    -   sizing or positioning of the template is changed.    -   any fixed variables are changed.    -   the input definition for predefined variables changes (i.e.,        input changes.)

However, these are infrequent events and likely do not occur during abroadcast. During playback, dynamic variables respond to variablechanges from external sources.

CCacheLayer, CCacheValue, CCacheSubFrame

A CCachelayer object represents one layer in the rendering of a title.Typically, this represents a variable that can change dynamically.

The rest of the template, including the design time variables, may allbe handled by one or more CCachelayers that have no variables. Thesefixed layers include, for example, the “background” layer as well as anyfixed semi-transparent layers that may appear before some other layers.

Multistate variables and Regular variables are two types of variableshaving the following attributes:

-   -   Regular variables get generated once and are used typically just        once. They include most information that gets displayed on        templates and are changed frequently, like Name, Message, Score,        etc.    -   Multistate variables typically go back and forth between a fixed        set of values, and they do it often. Two examples would be a        clock and a display of strikes in baseball.

With all this in mind, we have three kinds of CCacheLayers, and rulesfor their behavior:

-   -   Multistate variable layer. This has two or more Values that        represent each variation of the variable and they all get        rendered up front and saved to frame cache, so they can be used        again.    -   Regular variable layer. This has exactly one Value and gets        re-rendered when the variable changes. These are rarely saved to        the disk cache, because they won't last long.    -   Fixed/Background layers. These have all the steady state        variables, none of which it needs to track. These are        re-rendered whenever any of their variables change (which should        be infrequently) and always saved to file frame cache.

FIG. 5 illustrates a Multistate Variable example 500 applied to asporting event scenario. In FIG. 5, a Title Cache includes multiplelayers (“Clock”, “Down”, and “Background”). The Multistate Variable“Down”, for example, may be composed of four predefined values for thenumbers 1 through 4. Value “1” may be composed of a sequence of framesrepresenting the display of “Down” “1” over the time span of the layer.

CCacheValue

The CCacheValue keeps track of one value for a variable, managed byCCachelayer. Each CCacheValue carries all the information used togenerate it and, of course, the resulting set of partial frames, in theform of an array of CCacheSubFrame objects.

CCachelayer creates a set of one or more CCacheValues to represent eachpossible variable value.

CCacheSubFrame

CCacheSubFrame represents one point in time in a full CCacheValuesequence. It manages the storage of this frame either in memory or todisk. Note that this frame is typically just a subset of the full frameat a specific point in time.

This provides methods to write a frame as well as read it.

It also manages compression of the frame itself. It does so with severalmechanisms, all of which must respond in real time such as, for example,a

-   -   “Region of Interest” (ROI): Store only the rectangle within the        frame that is in use;    -   Data Compression: Fast lossless compression algorithms tend to        be efficient with graphics imagery because of the prevalence of        repeated pixel sequences; and a    -   Frame Duplication: Often, layers don't have any changes over a        period of frames, and so one value can be stored for all        identical frames.

FIG. 6 illustrates a block diagram of an object representation of theTitleCache class named TitleCache 601, according to an embodiment. TheTitleCache 601 in this illustration includes multiple layers (603, 605,607). Layers 603 and 605 with no variables are defined here as abackground while layer 607 includes multiple variables defined therein.Some of these variables include, for example, fixed 607, multistate 609and dynamic 611 variables. The multistate 609 variable, in this example,may have multiple values 613 that represent each variation of thevariable which all are rendered up front and stored to correspondingcells 619 within a frame cache 621, so they may be replayed at a latertime. In practice, the dynamic variable 611 generates frames that may bestored in memory 617, but not stored back to disk for later use, as partof the rest of the frame cache.

Integration of the TitleCache Class

FIG. 7 illustrates a block diagram of the integration and implementationof the TitleCache class in system 200, according to an embodiment. TheTitleCache class, in this example, may handle multipart rendering,caching, and playback of one specific title. It does it primarily underthe control of the Scheduler 205 and seamlessly operates with the RenderEngine 209, the Scheduler 205, the Output 211, and multiple TitleInstances 703 defined within a Title Cache object calledTitleInstanceManager 701.

Title Instance:

In FIG. 7, when the title instance is loaded, or created, itinstantiates a Title Cache object called TitleCache 705, for example, tomanage the rendering and caching of the title.

FIG. 8 illustrates a block diagram of a file representation of an XMLTitleCache definition 801, according to an embodiment. When the titlefirst loads, it sends the TitleCache 705 the cache file to load. Theentire cache is placed in one binary cache file 803, though there may bea separate XML definition 801 that controls the parsing of the data. Insome embodiments, the definition data may be stored in an alternateformat from XML. In other embodiments, it may be included in the binarycache file. In some embodiments, the one binary cache file 803 may becompressed to reduce storage requirements and enhance efficiency of theoverall system 200.

It also may be memory mapped, to improve performance. If compressed andthe compression is fast, then the compressed format might also be theformat that is kept in memory, when loaded, and then uncompressed priorto rendering.

In another instance, when the title is new or gets a new template, itmay notify the Title Cache to refresh itself. This regenerates therenders and saves to cache, as needed.

Accordingly, when the title is saved, it gets the cache file XML data701 from the Title Cache.

Next, to properly build a representation of the title, “TitleCache”calls the Title Instance. FIG. 9 illustrates a flowchart of building arepresentation of the title of system 200 which is also provided in thesteps below.

-   -   1. Get the names of all the segments, markers, and their time        points (901).    -   2. Get the names of all the variables and the time points for        their starts and ends (903).    -   3. Gets the names of all the variables in use by the Input        Behavior (905).    -   4. Of those variables, get the list of predefined values for        multistate variables (907).

Scheduler:

Referring again to FIG. 7, the Scheduler 205 may be used to manage theprimary access to the TitleCache. All internal and external calls tocontrol playback route through the Scheduler 205.

In some instances, the Scheduler 205 maintains a central list of allTitleCaches 703 and then parses incoming commands and sends them to theappropriate TitleCache instance 703. The Scheduler 211 may also manageaccess to the output of the TitleCaches 703, so that the output device211 can simply call the Scheduler 205 to retrieve the rendered frames.

During playback, the Scheduler 205 manages queuing and then forwardingSchedule requests to the TitleCache to control playback.

Render Engine:

Referring again to FIG. 7, the Render Engine 209 operates outside thetitle cache, since it can be a completely external technology, and sorequests to it are made asynchronously. To accommodate this, a queue ofrender requests is managed. The Render Engine 209 calls the TitleCache,from its own thread, and retrieves these requests, runs the renders, andthen calls back with the rendered frames.

A specialized class handling called CCacheRenderRequest, representing arender request, is a block of frames that are to be rendered for aparticular set of variable values of the time segment for the frames.

In some instances, the render engine generates all calls to TitleCache.These calls are thread safe and return quickly. With each framerendered, the render engine may generate a call back to the TitleCacheto pass the frame to it and determine whether to continue or switch to adifferent render. In another embodiment, the title cache generates callsto the render engine to render the frame sequences.

FIG. 10 illustrates a flowchart of the frame rendering by the renderengine of the title cache system 200 which is also provided in the stepsbelow.

-   -   1, Render Engine calls GetNextRenderRequest( ) (1001) which        returns CCacheRenderRequest (1003).    -   2. Render Engine prepares the variables (1005).    -   3. Then, for each frame in the request (1007),        -   a. Render the frame (1009).        -   b. Call TitleCache::SubmitRender(passing it both the Frame            and the CCacheRenderRequest) (1011).        -   c. Cache searches for the correct CCacheValue and, if it is            still there, sends it the frame (1015), which CCacheValue            copies in (1017).        -   d. Cache returns a success code to continue or a failure            code if this is no longer needed. Failure can also mean the            render is finished (1019).        -   e. If success, Render Engine moves to render the next frame            (1021).        -   f. If failure, Render Engine calls GetNextRenderRequest(            )(1023).

Note that the Render Engine retains the one instance ofCCacheRenderRequest, returning the one instance when done viaReturnRenderRequest( ). In some situations, this typically frees thememory. But, this also provides a way for the title cache to stop arender and then continue at a later time. It also provides a way for theRender Engine to return a render that it has not completed, because theRender Engine needs to work on something else that may have higherpriority. However, there can be other equally acceptable ways toorganize the queue of render requests between the title cache and theRender Engine.

Output Devices:

Finally, the Output Devices 211 component, as shown in FIG. 7, callsTitleCache::GetFrame( ) when Output Devices 211 requires a frame. Insome instances, the TitleCache may always return the frame immediately.In other aspects, if the TitleCache does not have the frame ready,TitleCache may return the previous frame, remaining active anduninterrupted.

The TitleCache may use a memory cache of two or more CCacheFrameBuffersto ensure that TitleCache is ready to play. A lower priority thread mayrun in the background, ensuring these are replenished.

The CCacheFrameQueue may generate and store a short queue of fullycomposited frames for playback. The intention is to make sure that thereis always a frame ready to go so the output is uninterrupted.

In some embodiments, there are three external objects that generallydrives the framebuffer:

-   -   The output. These include the output devices through which the        frames stream. It is constantly asking for a new frame.    -   The parent cache. Under the control of the scheduler, this is        frequently changing the status, from updating variables to        entering and leaving playback.    -   The refresh thread. This is a background thread that repeatedly        calls all of the frame buffers to refresh their frames.

In other embodiments, there may be three modes of activity: Off, Play,and Paused.

-   -   Off: the title isn't even active. Any requests for a frame for        output should get back a blank frame. Meanwhile, the buffer        should be primed with the first frames for playback.    -   Paused: the titles are active, but not moving. Requests for        frames always return the same frame, which is at the paused        point in the title.    -   Play: the title is moving forward. Every time a frame is        requested, the next in line is served and the background thread        is actively replenishing the queue.

Note that the actual mode is determined by the activity of the title.For example, as soon as something is scheduled to play, the play statebecomes Play. The actual mode remains in that state until the last layeris finished sending out frames. Once all layers are stopped, the modeenters with Paused or Off state. The Off state is the special case whereall layers have completed playing and entered the off state. The Pausedstate is the case where one or more layers still have the cursor, butare not moving.

CCacheRenderRequest represents a block of frames that is required to berendered for a CCacheValue. This object is sent to the render engine,giving it a fully self-contained description of what is required.

Cache Rendering Optimization:

From the above discussion, a summary of attributes for defining andoptimizing the cache rendering process in system 200 is provided below:

-   -   A variable is nothing more than a string of characters, i.e., an        array of byte characters that specifies a specific graphic (i.e.        text or image, etc.) to show over a range of time.    -   The data input 203 defines which variables it sends and what        values it puts in them.    -   The Title Template 235 defines which variables it supports and,        for each, how it may translate the incoming string into the        appropriate image to render.    -   The TitleCache 601 takes the set of variable value strings from        the data input 203 and sends them to the Render Engine 209 to        render an image, using the title template 235 to define the        render.    -   Later for playback, the TitleCache 601 matches live data strings        from the data input 203 with its cached images and copies it        into the frame.

In yet another example of the caching system 200 applied to a sportingevent scenario, the data input source 201 may be a sports scorecontroller, sending a numeric value to indicate a game quarter.Depending on its layout and intended usage, the title design might haveseveral choices for how it displays the first quarter:

-   -   1 (text string of “1”)    -   1st (text string of “1st” where the ST are a much smaller font        size)    -   First Quarter (translated into a completely different text        string)    -   [image] (an image that shows the quarter status.)

In all cases, the representation of the original string is defined bythe title design and the cache should not be involved. Instead, titledesign should request a render of “1” and return whatever interpretationthe design has for what first quarter should look like. And, as with theprevious clock timer example, it may be constraining for the cache tointerpret how large or small the rendered image will be or where itshould be placed.

Data Independent Rendering

For the game quarter case, the cache may represent all values for allvariables as simply text strings, with no comprehension as to theirmeaning. And so, it is agnostic as to the meaning of any string passedto it by an input source. It simply passes it to the rendering engine,along with the selected template.

The title template may incorporate a translation table, equatingspecific input strings with specific values to render an image. Thisallows one configuration to convert a “1” into a simple displayedstring, while another configuration to convert it into an image.

With that in mind, the steps for preparing the cached image of the value“1” for variable “quarter” include:

-   -   1. The input sends the text string “1” for the variable        “quarter”    -   2. The cache simply passes it to the title template and requests        it to render “1”.    -   3. The render engine consults the translation table in the title        template, which converts the “1” into the appropriate rendered        text or image.    -   4. The render engine sends back the rendered image.    -   5. The cache stores the rendered image, with optional        optimizations of compression and calculating and storing just        the ROI.    -   6. On playback, the input sends “1”    -   7. The cache selects the image for “1” and builds the full image        by layering this image on top of the remainder of the scoreboard        components.

For the game clock scenario, the title cache is also unaware of what itis displaying, similar to the game quarter case. In the game clock case,additional items are considered. For example, if a rendering of everyvariation of the clock is created, 10,000 frames are potentially createdfor all the combinations of values in a four-digit clock. In thissituation, the cache system 200 may subdivide the problem and addresseach digit independently. Then, the title cache system 200 may prepareonly a smaller portion of different variations, (e.g., 10 variations),one for each numeric value. However, because the title cache does notknow how these are drawn or what they really represent, the title cachedoes not have the ability to reuse the same digit in all four positions.

To address this limitation of the title cache, and still keep the titlecache completely independent of the data, a Multipart Variable cachingis introduced as another component of the system 200. In one instance,the multipart variable caching may break a string into severalsub-segments and create a set of variation renders for each string.Then, on playback, the Multipart Variable caching may select thevariations that together match the requested input and merge them intoone image. For Multipart Variables,

-   -   a. The Input can specify a variable as composed of individual        letters, or related sets of one or more letters, as long as they        combine to match all possible input patterns.    -   b. The Input specifies all values for each letter (or set), so        that each digit can be independently rendered.    -   c. The Input may provide a format string that is used to set the        spacing of the letters during rendering.    -   d. Each letter (or set) is rendered separately with its own time        sequence.    -   e. When an individual letter (or set) changes, it can play out        and then the replacement plays in.    -   f. If a letter (or set) does not change, it remains unchanged at        the pause point.    -   g.

FIG. 11 illustrates a block diagram of the Multipart Variable named“Clock”, according to an implementation. In the game clock example,

-   -   1. When building the cache:        -   a. Break the string down into separate segments. (i.e. the            clock digits)        -   b. For each segment, provide all possible value variations.        -   c. Render each variation for each segment.        -   d. Represent each variation as the full string but with            empty spaces for the parts outside the segment. (i.e.,            —“1______”, “2______”, all the way up to “______1”,            “______2”)        -   e. Store each of these variations as the partial string and            its associated image.    -   2. On playback, in response to a text value from the input:        -   a. Search through the list of variations.        -   b. For each variation that provides characters that match            exactly in value and position the input value:            -   i. Select the variation.            -   ii. Remove the matching characters from the search.            -   iii. Continue until all characters are matched.        -   c. Create a composite by adding all of the selected            variation images together into one image.

In the cache system 200, the process may construct a composite of imagesto correctly represent the string that is passed by layering togetherall variations, using the matching of substrings to recreate the set ofsub-images that build the equivalent image. The solution presented sofar only works if the size of each digit is exactly the same. Forexample, draw the time string “12:34” in a proportional font, then drawjust the last digit with the string “4” results in string placementerrors. To overcome this placement error, the optional concept of aformat string is applied to the system 200. The format string mayprovide an interpretation of the render that should be used to determinea positioning of each segment during render. Such positioning adjustmentis referred to in this document as a Multipart Alignment.

In one instance of the Multipart Alignment, the format string may besimply a string with all characters filled in that shows anappropriately spaced rendering. For example, with the clock format, itcould be “00:00”.

To implement the Multipart Alignment in system 200:

-   -   1. For each render, include both the substring, i.e., “4”, and        the format string, i.e., “00:00”.    -   2. The render operation first organizes the spacing of the        proportional characters for “00:00”.    -   3. Then the render replaces the letters of the format with the        letters of the substring.    -   4. It then renders with the letters in these positions.    -   5. The ‘4’ is placed exactly in the position of the 4th ‘0’ from        the format, as it should be.

FIG. 12 illustrates a display output of the current time in aninternational city. Here, two variables are defined: City and Time. TheCity is simply a string from the input with the name. This is updatedvery infrequently, so it is not pre-cached. Because the Time isconstantly changing, it may be required to pre-cache its values in orderto be able to call them up and display them immediately. Between sixdigits and the colon pattern, “: :”, the input specifies 61 uniquevariations which can be combined to build all permutations. These uniquevariations are all rendered and saved in the cache. Subsequently, duringplayback, the unique variations may be used by a multi-cache to assemblefull composited images, as shown here for the string “17:31:57”.

FIG. 13 illustrates a block diagram of the intelligent title cachesystem 200 and external render engines, according to another embodiment.The intelligent title cache system 200 may be coupled with one or moreexternal render engines 1301 and configured to control the selectivelayer by layer rendering of variable data in the rendering engines, soas to build the necessary frame cache. These external render engines1300 may include, for example, third party software or hardware visualeffect or animation tools.

FIG. 14 illustrates a flowchart of the intelligent title cache system200. A process flow of the intelligent title cache system 200 may besub-divided into four operational groups as indicated by dotted lines inFIG. 14. These include, for example, a TitleInstanceManager group 1401,a Scheduler group 1403, a Render Engine group 1405, and Output Devicesgroup 1407. Each of the four operational groups represents the processflow operation of their corresponding components. For example, theTitleInstanceManager group 1401 represents the process flow for theTitleInstanceManager 701, the Scheduler group 1403 represents theprocess flow for the Scheduler 205, the Render Engine group 1405represents the process flow for the Render Engine 209, and the OutputDevices group 1407 represents the process flow for the Output Devices211 as shown in FIG. 7. Starting at 1411, the system 200 checks when anevent at a title instance is a load event or create event. If no titleinstance is present at step 1411, the TitleInstanceManager 701 waits(step 1413) until one becomes available. When a valid title instance isloaded or created, the TitleInstanceManager 701 instantiates a TitleCache object called TitleCache (step 1415) which sends the TitleCachecache file (step 1417) to load and allocates the entire cache in onebinary cache file (step 1419). Note, at this stage and prior to steps1421-1429, the cache structure is not yet known because the content maynot yet exist as to what to store in the cache structure. Once theTitleCache connects to the input, then it may differentiate of whichinput variables to separate out into the cache, and what values to sendto the cache. After instantiating the Title Cache, theTitleInstanceManager 701 assembles a representation of the title:TitleCache calls Title Instance (step 1421) which includes, for example,acquiring names of all segments, markers, and their time points (step1423), acquiring names of all variables and time points for their startsand ends (step 1425), getting names of all variables in use by InputBehavior (step 1427), and of those variables, getting a list ofpredefined values for the multistate variables (step 1429). In theScheduler group 1403, the Scheduler 205 is configured to manage primaryaccess to the TitleCache, including, for example, routing all internaland external calls through the Scheduler to control playback (step1431), managing primary access to TitleCache (step 1433), maintaincentral list of all TitleCaches and then parsing incoming commands andthen sending them to appropriate TitleCache instance (step 1435),managing access to output of TitleCaches, so that output device can callthe Scheduler to retrieve rendered frames (step 1437), managing queuingduring playback (step 1439), and forwarding schedule requests toTitleCache to control playback (step 1441). In the Render Engine group1405, the Render Engine 209 is configured to perform all 3D renderingoperations in the system 200, including, for example, calling TitleCacheand retrieving rendering requests (step 1443), executing requestedrenders (step 1445), and calling back with the rendered frames (step1447). Finally, in the Output Devices group 1407, the Output Device 211is configured to retrieve and stream multiple frames which is managedand made accessible by the Scheduler 211. For example, after frames arefully rendered by the Render Engine 209, the Output Devices 211 may callTitleCache::GetFrame( ) when the Output Devices 211 requires a frame(step 1449).

Several features, attributes, and benefits of the system 200 aresummarized below:

-   -   A Title is composed of a template and a number of variables in        the template.    -   Input determines which variables are dynamic.    -   Dynamic variables are each rendered in their own layer.    -   All other variables are set once and rendered in a background        layer.    -   Dynamic variables can play in sync with the rest of the title,        or independently.        -   Playback of the title is from the start to a pause point,            and then to the end.        -   Dynamic variables may start, pause, and stop payback            independently.        -   Start and stop times for dynamic variables may optionally be            the actual start and stop times of the variables themselves            within the template.        -   Playback of a variable considers its relation to the pause            point. For example:            -   To change a visible value, play from pause to out (end                point of variable in the time line), then insert new                value and play from in (start point of the variable in                the time line) to the pause point.            -   To momentarily view the value, play from in to out,                without stopping.    -   Input can specify a set of expected values for a variable, so        they can be precomputed and cached.        -   When variables are not cached, playback request waits for            the new value to render, then plays it.            -   The playback includes options for waiting for render,                waiting to sync several parallel variable renders,                playing without waiting, playing part way through, etc.    -   Multipart variables        -   Input can specify a variable as composed of individual            variable subsets such as individual alphanumeric letters or            subsets of letters.        -   Input specifies all values for each letter/subset, so that            each letter/subset can be independently rendered.        -   Input may provide a format string that is used to set the            spacing of the letters during rendering.        -   Each letter/subset is rendered separately with its own time            sequence.        -   When an individual letter/subset changes, it can play out            and then the replacement plays in.        -   If a letter/subset does not change, it remains unchanged at            the pause point.    -   Benefits and Advantages of system 200        -   Data independent rendering.        -   Highly efficient playback driven by intelligent            understanding of the component data and recognition that            full render of a complex scene is much more compute            intensive than overlaying precomputed bitmaps.            -   Isolate different data (variables) into their own                layers.            -   Things that never change are rendered once and stored.            -   Things that have all values known before also rendered                once and stored.            -   Complicated multiple part data, such as time clocks,                broken into parts and pre-rendered.            -   Things that are truly dynamic are rendered on the fly                -   Typically just a short text sequence —simple and                    fast.                -   Automatic—system inserts the render prior to play.                -   Deliberate—requests the render then follows with                    play.            -   Supports complex, multiple asynchronous animations as                easily as a still image.                -   Render is simply a look up of each variable image at                    its point in its sequence.        -   By offloading the 3D graphics (or other render technology)            engine, it is possible to run this on a wide range of            computers, from simple processors with onboard graphics            software to powerful GPU systems.            -   Playback is almost always the same. (Exception is                insertion of updated variable value.)            -   Preparation/pre-render will take longer on slower                machines.

All patents, patent applications, and other references cited herein areincorporated by reference in their entireties.

What has been described and illustrated herein is a preferred embodimentin this document along with some of its variations. The terms,descriptions and figures used herein are set forth by way ofillustration only and are not meant as limitations. Those skilled in theart will recognize that many variations are possible within the spiritand scope of the embodiments in which all terms are meant in theirbroadest, reasonable sense unless otherwise indicated. Any headingsutilized within the description are for convenience only and have nolegal or limiting effect.

Other embodiments and modifications of the present document may occur tothose of ordinary skill in the art in view of these teachings.Accordingly, the embodiments in this document are to be limited only bythe following claims which include all other such embodiments andmodifications when viewed in conjunction with the above specificationsand accompanying drawings.

What is claimed is:
 1. In a title cache system for managing a titlehaving a template and a plurality of variables associated with thetemplate, a method comprising: instantiating a title cache object by atitle instance manager in response to a title instance event, whereinthe title instance event includes a load event and a create event;managing access to the title cache object, including routing a pluralityof internal calls and external calls through a scheduler to control aplayback of a plurality of frames; rendering the plurality of framesinto a series of rendered frames by a render engine; and retrieving theplurality of frames by one or more output devices for streaming theplayback, wherein the scheduler is configured to manage a queuing duringthe playback and configured to forward a plurality of schedule requeststo the title cache object to control the playback.
 2. The method ofclaim 1, wherein the title instance manager is configured to transmit tothe title cache object a cache file to load in response to the loadevent, wherein the cache file is allocated to a binary file.
 3. Themethod of claim 1, wherein the title instance manager is configured todetermine which of the plurality of variables associated with thetemplate are a plurality of dynamic variables and which of the pluralityof variables associated with the template are a plurality of regularvariables based on a data input.
 4. The method of claim 3, wherein eachof the plurality of dynamic variables are rendered in a dynamic layer.5. The method of claim 3, wherein each of the plurality of regularvariables are rendered in a background layer.
 6. The method of claim 3,wherein the plurality of dynamic variables are configured to play insync with the title or play asynchronously.
 7. The method of claim 1,wherein the playback is configured to wait for the series of renderedframes, wait to synchronize to a plurality of parallel variable renderedframes, play without waiting for the series of rendered frames tocomplete rendering on the render engine, and play a portion of theseries of rendered frames.
 8. The method of claim 1, wherein the titlecache object includes a multipart variable caching component and aninput associated with the multipart variable caching component.
 9. Themethod of claim 8, wherein the input associated with the multipartvariable caching component indicates a plurality of individual variablesubsets.
 10. The method of claim 9, wherein each of the plurality ofindividual variable subsets is rendered separately having a unique timesequence.
 11. A title cache system for managing a title having atemplate and a plurality of variables associated with the template, thesystem comprising: a title instance manager configured to instantiate atitle cache object in response to a title instance event, wherein thetitle instance event includes a load event and a create event; ascheduler configured to manage access to the title cache object,including routing a plurality of internal calls and external callsthrough the scheduler to control a playback of a plurality of frames; arender engine configured to render the playback of a plurality of framesinto a series of rendered frames; and one or more output devicesconfigured to retrieve the plurality of frames for streaming theplayback.
 12. The system of claim 11, wherein the title instance manageris configured to transmit to the title cache object a cache file to loadin response to the load event, wherein the cache file is allocated to abinary file.
 13. The system of claim 11, wherein the title instancemanager is configured to determine which of the plurality of variablesassociated with the template are a plurality of dynamic variables andwhich of the plurality of variables associated with the template are aplurality of regular variables based on a data input.
 14. The system ofclaim 13, wherein each of the plurality of dynamic variables arerendered in a dynamic layer.
 15. The system of claim 13, wherein each ofthe plurality of regular variables are rendered in a background layer.16. The system of claim 13, wherein the plurality of dynamic variablesare configured to play in sync with the title or play asynchronously.17. The system of claim 11, wherein the playback is configured to waitfor the series of rendered frames, wait to synchronize to a plurality ofparallel variable rendered frames, play without waiting for the seriesof rendered frames to complete rendering on the render engine, and playa portion of the series of rendered frames.
 18. The system of claim 11,wherein the title cache object includes a multipart variable cachingcomponent and an input associated with the multipart variable cachingcomponent.
 19. The system of claim 18, wherein the input associated withthe multipart variable caching component indicates a plurality ofindividual variable subsets.
 20. The system of claim 19, wherein each ofthe plurality of individual variable subsets are rendered separatelyhaving a unique time sequence.